Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 146-tree-1
name: 1499
tree-preservation-order: undefined
146-tpo-1
uprn
address-text
point: POINT (-0.971606 50.865023)
geometry: MULTIPOLYGON (((-0.971535 50.865015,-0.971539 50.865029,-0.971548 50.865042,-0.971564 50.865052,-0.971583 50.865059,-0.971605 50.865061,-0.971627 50.865059,-0.971647 50.865053,-0.971663 50.865043,-0.971674 50.865031,-0.971677 50.865017,-0.971674 50.865003,-0.971664 50.864990,-0.971649 50.864980,-0.971629 50.864974,-0.971607 50.864971,-0.971585 50.864973,-0.971565 50.864979,-0.971550 50.864989,-0.971539 50.865002,-0.971535 50.865015)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL